I know it's been a few days but finally found some time again.

I'm looking at my /opt/retropie/configs/snes/retroarch.cfg

input_player1_b = "shift" input_player1_b_btn = "nul" input_player1_b_axis = "nul" input_player1_y = "ctrl" input_player1_y_btn = "nul" input_player1_y_axis = "nul" input_player1_select = "5" input_player1_select_btn = "nul" input_player1_select_axis = "nul" input_player1_start = "1" input_player1_start_btn = "nul" input_player1_start_axis = "nul" input_player1_up = "up" input_player1_up_btn = "nul" input_player1_up_axis = "nul" input_player1_down = "down" input_player1_down_btn = "nul" input_player1_down_axis = "nul" input_player1_left = "left" input_player1_left_btn = "nul" input_player1_left_axis = "nul" input_player1_right = "right" input_player1_right_btn = "nul" input_player1_right_axis = "nul" input_player1_a = "z" input_player1_a_btn = "nul" input_player1_a_axis = "nul" input_player1_x = "alt" input_player1_x_btn = "nul" input_player1_x_axis = "nul" input_player1_l = "space" input_player1_l_btn = "nul" input_player1_l_axis = "nul" input_player1_r = "x" input_player1_r_btn = "nul" input_player1_r_axis = "nul"

This is what's exactly in the file for the button mapping for P1 and when I go into Super Street Fighter alpha 2 it doesn't work. Made a rom specific cfg too and still doesnt work. Now here's the super weird part ... tried Star Fox 2 and controls seemed to work fine. Tried Super Star Wars and same problem as SFA2.

Edit: Also how do I go about reinstalling an emulator?

@mitu I redid the controls again for the "v" key (from everything I can tell this is not used elsewhere). This time I used the in game menu with the tab key. Still the right direction does not work. Also I have several existing directional buttons mapped to keys that are used for other functions but all of those keys are functioning normally.

@kombat Yes. I flashed to 1.39. You can still use it as a keyboard if desired, but the option to change the buttons to gamepad buttons is now available.

Emulationstation also sees my mini-ipac as two"Ultimarc Mini-Ipac"s now instead of "keyboard"

@douga Pi Model 3
Power Supply used: 5V
RetroPie Version Used 4.4
USB Devices connected: IPac2, Sanwa joystick

I have an old model IPAC4 that I used back in 2008 running Win98, XP, etc. and I eventually rebuilt my system around the PI (you can see details linked in my profile or signature below). Anyway, my IPAC has the PS2 connector but works with a USB adapter cable.

Here is the thing--the IPAC is a keyboard. Or at least it looks like one to the computer to which it is connected. Your joysticks, assuming they are microswitch-based, could be pushbuttons. There is nothing about the fact that it is a stick vs. a button--it is simply shorting the input on the IPAC to ground.

So, what happens if you wired a joystick to BUTTON1,2,3,4 on the IPAC? I would think this would let you trigger those buttons when you move the stick to short the respective inputs. If true, you should conversely be able to wire a button to one of the joystick inputs and pressing the button should trigger that key. And this brings me to my point. . . Do you know what keyboard keys are getting sent by each directional trigger? How are you testing on the Pi? Are you opening a text file in Pixel for example? My player 1 joystick maps to the arrow keys I think. So, if I open a text fine on the Pi, I can move the cursor around just like I am typing arrow keys.

I know I am not offering an answer but more of a testing method. Mapping keys can get really confusing once you launch an emulator, so my approach is to verify the raw inputs are getting out of the IPAC and into the Pi.

One approach to testing keyboard inputs is to launch the keyboard testing executable from AdvanceMAME at commandline. This will let you watch on screen what the PI is receiving when you pound on buttons or move your sticks. I don't remember the test command off-hand, but if you dig into the Docs here on the RetroPie and look for the Spinners/Trackball page, there is a similar test you can run for Mouse input. I know, we are not testing a mouse, but there are three executables in there for AdvanceMAME that let you test each Mouse, Joy and keyboard inputs. Might be worth a little time looking that up. Sorry , don't have my Pi handy to check.

My thought is that once you know the inputs are getting sent, you are no longer troubleshooting the IPAC, but rather the mapping. Knowing that much can go a long way to figuring out the next step.

@axrst ARCADE is not an emulator, its a folder where you place roms and then choose an emulator to run them using the run command. If you are electing to choose a non-libretro emulator such as mame4all or pifba, they will not be configured on startup.

https://retropie.org.uk/docs/Arcade/

https://retropie.org.uk/docs/Runcommand/

mame2003-plus has a new input mode specifically for this purpose.

It is activated via a core option which allows the core to process input through the either mame_keyboard interface or the retropad -- or both simultaneously as with classic mame2003 (although that is not as useful as you are finding out).

that fixed it! Not sure how I missed that in the config file. I mapped it to Nul and it works ! Thank you!!!!!

Now vice won't save the mapped hot keys. I load up the virtual keyboard, select a key, press M then press a button to map. In game it works fine. I press f12, then settings management, and save hot keys, and then I exit and reenter, and the key is no longer saved. Any ideas?

@dj-wheels That's too bad about the microswitches. I got all of my pushbutton and joystick components from them (this was ages ago) and I have not had problems. I think I had one switch failure since 2009 out of 48 switches (cherry).

Thanks a lot for all your help guys... in this case it was Apple at fault and I'm going to tell you how you can fix it.

Apple in their infinite wisdom decided that people don't simply want quotes! Why have a quote when you can have a smart quote :). It's all well and good changing something like this although when you start working on config files which require the default quote, things will go very wrong fast!

Id suggest that if you are using an Apple system and connecting through a server to make your changes and are facing issues like I mentioned, look very carefully at the quotes and see if they are different from the other untouched entries, if they are, simply follow this guide to change them back to normal:-

https://derflounder.wordpress.com/2014/02/01/disabling-smart-quotes-in-mavericks/

Thanks again guys so much for your help, sometimes it simply needs another set of eyes, I must have sunk in 10+ hours on this and must have looked at that config a thousand times although it never registered :D

Glad my build is back on track :)

@horaceandspider

Thanks - The other thing that I have been testing is the abilty to swap the A & B buttons, as outlined in you replay below. I can't get this to work. Here is my .uae for Turrican II which section would I need to edit to swap these buttons around?

https://pastebin.com/nQsw61K4

@horaceandspider said in Amiberry & Ipac:

@tuki_cat Yes, it is meant to be that way.

Using the ReroArch layouts which are documented in RetroPie, B is the “bottom” button (Cross for a PS pad) ... which I would call “South”

On the Amiga Cd32 pad, this is always “Red” aka Fire and the East/Circle (Retroarch A) button is always Blue.

It therefore retains this layout position when using the normal Amiga joystick layout.

At the moment, I have “locked” the keyboard control this same way around.

You can read your controller layout in Amiberry from a seperate location, and manually chose to change the two around, if you prefer, and I will probably need to make the same allowance for keyboard mapping :)

@AndersHP Yes, all osd messages.

@Waylander

Nice build, I went lazy. Bought a tank stick and shoved my pi2 inside lol

Think I've solved it

@sinfolmatt I've just watched a video and found out that the USB speakers that come with an audio jack, the audio jack just plugs straight into the raspberry pi 3 as it has an audio jack point so nice and easy. It's looking like the way to go is foe mo get a Raspberry pi 3 on order and crack on with it.